Retires this repo's local cli-schema.ts implementation in favor of
@cli-schema/spec, @cli-schema/zod, and @cli-schema/commander (extracted from
this exact codebase, published at github.com/cli-schema/cli-schema-js).

- factory.ts: the _commandConfig non-enumerable attach point is replaced with
  @cli-schema/commander's attachInput/attachIntent (the sole prior reader,
  cli-schema.ts, is the only thing that changes here -- runtime option/argument
  registration and request handling are untouched).
- lib/schema-args.ts: thin wrapper re-exporting @cli-schema/zod's generic
  extractor, adding back Elastic's found_in/sort-pairs enrichment and reserved
  flag list via the package's enrich/reserved hooks.
- cli-schema.ts: shrinks from ~600 lines to the ENVIRONMENT constant plus a
  handler that calls the package's buildCliSchema, passing classifyRole (to
  keep --dry-run as the only name-based role, matching prior emission),
  enrichSchemaArg, and postProcessInputParameter (for the body-routed CSV
  separator) -- all the local types/JSON-Schema helpers/walkers/hoisting logic
  the package now does are deleted.
- cli-schema-intent.ts: deleted; es/register.ts and kb/register.ts now import
  inferIntentFromHttp from @cli-schema/spec (byte-for-byte identical behavior).

This surfaced and fixed a real bug in @cli-schema/commander 0.1.0 (shipped as
0.1.1): every ES/KB command's Zod-schema-derived flags are registered as real
but *inaccurate* Commander options here (always optional, no Commander-visible
default, since actual required/default/enum enforcement happens via Zod after
merging flags with --input-file/stdin input) -- the package's old
"skip if a real option already covers this flag" rule silently discarded that
richer schema detail for nearly every parameter in this CLI. Fixed upstream via
a mergeParameter hook (schema wins on richness, Commander wins on
role/shortName/hidden) rather than picking one source over the other.

docs/cli/schema.json is regenerated, not byte-identical (root key order and
empty-array omission now follow the spec's canonical shape), but every
parameter's content is preserved exactly: 6915 parameters before and after,
identical counts for separator (50), repeatable (391), number (358), and enum
(61) fields, and the full document validates against @cli-schema/spec's own
meta-schema validator. The only 7 real diffs are ES's own native "dry_run"
query/body fields (e.g. cluster reroute, ILM migrate-to-data-tiers) gaining
role: "dryRun" instead of "flag" -- previously only the framework-injected
--dry-run flag got that classification; the merge fix applies the same
role-by-name heuristic uniformly regardless of which side registered the flag.

Added a regression test asserting the body-routed/query-routed separator
distinction survives end-to-end through the new wiring. Regenerated NOTICE.txt
for the three new bundled dependencies.

…o across 2 attempts; see PR discussion)